Release 10.1A: OpenEdge Deployment:
WebClient Applications

Choosing secure communication protocols

To guard against the inherent security problems associated with network traffic and to provide a greater level of security for your applications, you can encrypt an application’s configuration file and application-component downloads by using a secure communication protocol. For example, you can use the HTTPS communication protocol to encrypt network traffic, using a combination of symmetric and asymmetric ciphers. For more information on symmetric and asymmetric ciphers, see the "Digitally signing files" section.

Secure protocols that you can use, depending on the server type (Web server, file server, or AppServer) where the files are hosted, include:

HTTPS (requires the use of an AIA)
AppServerS (codebase downloads only)
AppServerDCS (codebase downloads only)

For more information on choosing a communication protocol for application configuration file and codebase downloads, see Chapter 4, " Designing the Deployment Configuration." For more information on the HTTPS protocol and the AIA, see OpenEdge Application Server: Administration .